Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[11.0][mig] purchase_order_block] #480

Merged

Conversation

JordiBForgeFlow
Copy link
Member

@JordiBForgeFlow JordiBForgeFlow commented Nov 23, 2017

Replaces #476
Depends on the following PR's:

Purchase Order Approval Block

This module allows you to block the approval of an RFQ when an Approval
Block Reason has been provided. Upon confirmation of an RFQ the orders will be
waiting for approval by a Manager.

Configuration

  • Go to ‘Purchases / Configuration / Purchase Approval Block Reasons’ and create
    the blocking reasons as needed, providing a name and a description. A field
    ‘Active’ allows you to deactivate the reason if you do not plan to use it
    any more.
  • Assign the security group 'Release blocked RFQ' to users that should be able
    to release the block. Users in group 'Purchase / Managers' are by default
    assigned to this group.

Usage

Set the Purchase Approval Block

#. Go to ‘Purchases / Purchase / Requests for Quotation’
#. Create a new RFQ and indicate the approval block reason (found in the
right hand side of the screen, below the order date).

Search existing RFQ

There is a filter ‘Blocked’ to search for orders that are blocked for approval.
It is also possible to search RFQ’s with a specific block reason.

Confirm the RFQ

#. Press the button ‘Confirm’. If there’s an approval block, the order will
be set to status 'To Approve'. You will then need to request a Purchase
Manager to approve it.

Release the purchase approval block

While the RFQ is in draft, members of security group ‘Release blocked RFQ’,
can see a button ‘Release Approval Block’. From this point and on, anyone
seeing that RFQ will be able to validate it.

Notifications to followers

Followers of the RFQ receive notifications when an approval block has been
set or released.

@JordiBForgeFlow JordiBForgeFlow force-pushed the 11.0-mig-purchase_order_block-refactor branch 3 times, most recently from 902596a to 2a92eb0 Compare November 23, 2017 11:47
@JordiBForgeFlow JordiBForgeFlow added this to the 11.0 milestone Nov 23, 2017
JordiBForgeFlow added a commit to ForgeFlow/purchase-workflow that referenced this pull request Nov 23, 2017
@JordiBForgeFlow JordiBForgeFlow force-pushed the 11.0-mig-purchase_order_block-refactor branch from 2a92eb0 to 207f6e0 Compare November 23, 2017 11:59
Copy link

@rgarnau rgarnau left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks nicer now 👍

Copy link
Member

@etobella etobella left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM 👍
Runbot is failing and OCA/server-tools#1025 is already merged

@rgarnau rgarnau mentioned this pull request Dec 19, 2017
1 task
@JordiBForgeFlow JordiBForgeFlow force-pushed the 11.0-mig-purchase_order_block-refactor branch from 207f6e0 to 864de85 Compare January 9, 2018 15:01
@JordiBForgeFlow JordiBForgeFlow force-pushed the 11.0-mig-purchase_order_block-refactor branch from 864de85 to 22fdfd6 Compare January 9, 2018 16:56
@JordiBForgeFlow JordiBForgeFlow merged commit e53d2b7 into OCA:11.0 Jan 9, 2018
JordiBForgeFlow added a commit to ForgeFlow/purchase-workflow that referenced this pull request Jan 9, 2018
@emagdalenaC2i emagdalenaC2i mentioned this pull request Dec 29, 2018
54 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants